Technical writers are often judged on the quality of the finished documentation. It is what customers, support teams, auditors, and internal users see. However, a lot of documentation problems begin much earlier. They begin when the writer is handed a Jira ticket or a pull request, a wiki page or a Word document, and they… Read more »
Cherryleaf Blog
How much time can technical writing teams really save with AI?
AI can make technical writers faster. It cannot remove the hard part of technical writing. The hard part is knowing what is true, what matters to the user, and what needs to be maintained after the product changes. For documentation teams, that distinction matters. AI can reduce the time spent on first drafts, summaries, rewrites… Read more »
Why AI agents need SOPs
AI agents are starting to do real work. They can search systems, draft answers, update records, test software, summarise documents, create pull requests, and trigger other tools. In some organisations, they are already moving from experiment to everyday workflow. That causes a documentation challenge. If an AI agent is going to act on behalf of a… Read more »
Claude Tag and technical writing: useful assistant or knowledge trap?
Last week, Anthropic launched Claude Tag for Slack. For documentation teams, it is worth paying attention to. At first glance, it looks like another AI assistant added to a workplace tool. You mention @Claude in a Slack channel, ask it to do something, and it replies in the thread. That undersells the change. Claude Tag… Read more »
AI in technical communication: the experiment is over, but the working method is still missing
Cherryleaf’s 2026 survey of AI in technical communication reveals technical communicators are no longer asking whether AI has a place in documentation work. Most are already using it. In our 2026 survey, 62% of the respondents said they use AI regularly or daily in their role. Only 8% said they do not use it at… Read more »